Skip to content

Fix catalog staleness option (1.5)#518

Merged
staticlibs merged 1 commit into
duckdb:v1.5-variegatafrom
staticlibs:staleness_default
Jul 19, 2026
Merged

Fix catalog staleness option (1.5)#518
staticlibs merged 1 commit into
duckdb:v1.5-variegatafrom
staticlibs:staleness_default

Conversation

@staticlibs

Copy link
Copy Markdown
Member

This is a follow-up PR to #514:

  • it changes the default scope of pg_staleness_query_enabled and pg_staleness_query options to GLOBAL to be easily usable from DuckLake (where SESSION options are not propagated to Postgres)
  • it changes the default value of pg_staleness_query_enabled to not run the staleness query by default in non-DuckLake scenarios

This is a follow-up PR to duckdb#514:

 - it changes the default scope of `pg_staleness_query_enabled` and
   `pg_staleness_query options` to `GLOBAL` to be easily usable from
   DuckLake (where `SESSION` options are not propagated to Postgres)
 - it changes the default value of `pg_staleness_query_enabled` to not
   run the staleness query by default in non-DuckLake scenarios
@staticlibs
staticlibs merged commit 41223e5 into duckdb:v1.5-variegata Jul 19, 2026
7 checks passed
@staticlibs
staticlibs deleted the staleness_default branch July 19, 2026 08:49
lnkuiper pushed a commit to duckdb/duckdb that referenced this pull request Jul 20, 2026
This PR updates the Postgres extension adding the following fix, where
the option registration was incorrect:

 - duckdb/duckdb-postgres#518
lnkuiper added a commit to duckdb/duckdb that referenced this pull request Jul 20, 2026
This PR updates the Postgres extension adding the following fix, where
the option registration was incorrect:

 - duckdb/duckdb-postgres#518
staticlibs added a commit that referenced this pull request Jul 20, 2026
This is a forward-port of PR #518.

This is a follow-up PR to #514:

 - it changes the default scope of `pg_staleness_query_enabled` and
   `pg_staleness_query options` to `GLOBAL` to be easily usable from
   DuckLake (where `SESSION` options are not propagated to Postgres)
 - it changes the default value of `pg_staleness_query_enabled` to not
   run the staleness query by default in non-DuckLake scenarios
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant